Welcome to the Microsoft® BizTalk® Server 2004 installation guide. It provides guidelines for hardware and software requirements, and instructions for installing and removing BizTalk Server 2004.
To ensure that you are reading the most up-to-date information, download the latest version of the Microsoft® BizTalk® Server 2004 Installation Guide, at http://go.microsoft.com/fwlink/?linkid=22120.
This section contains:
This checklist describes the steps required to set up a complete installation and configuration of Microsoft BizTalk Server 2004 and all its components. Each step points to instructions that you need to complete the step. For best results, print this checklist for referencing during setup.
| Step | Reference | |
|---|---|---|
| Check hardware requirements. | Minimum Hardware Requirements | |
| Check software requirements. | Minimum Software Requirements | |
| View Readme file for latest developments. | The Readme file is located on the root directory of the BizTalk Server 2004 installation CD. | |
| Install the Microsoft Windows® operating system. | Windows Prerequisites and Installation Requirements | |
| Install Internet Information Services (IIS). | Installing Internet Information Services (IIS) | |
| Install Microsoft Visual Studio® .NET 2003 with C#. | Installing Visual Studio .NET 2003 | |
| Install Microsoft SQL Server 2000 with Service Pack 3a. | SQL Server Prerequisite and Installation Requirements | |
| Verify that SQL Server is running. | Verify that SQL Server is Running | |
| Install Windows SharePoint Services. | SharePoint Services Prerequisites and Installation Requirements | |
| Install Windows Update Components. | Minimum Software Requirements | |
| Verify permissions on remote computers. | Minimum Security Requirements | |
| Install BizTalk Server 2004. | Performing a Complete Installation | |
| Configure BizTalk Server |
BizTalk Server Documentation is available from the Start menu after you install BizTalk Server. |
|
| Back up the Master Secret Key |
BizTalk Server Documentation is available from the Start menu after you install BizTalk Server. |
This section includes information about minimum hardware and software requirements for installing Microsoft BizTalk Server 2004. To ensure adequate performance, verify that the computers on which you install BizTalk Server 2004 meet these minimum hardware and software requirements.
This section contains:
The minimum hardware requirements for a complete installation of Microsoft BizTalk Server 2004 include:
This section contains the minimum software requirements for a server computer. This section also provides additional information for the client computers needed for Business Activity Services (BAS), and Single Sign-On (SSO) client utility.
International You can install and configure the English version of BizTalk Server on any other language platform. However, if you are not using the English version of BizTalk Server the platform language must match the BizTalk Server language.
The minimum software requirements for a complete installation of BizTalk Server 2004 on a single computer include:
Important Windows Server 2003 is required for Business Activity Services and Windows SharePoint Services .
Important Windows Server 2003 Web Edition is not compatible with BizTalk Server 2004.
Important SQL Server 2000 Personal Edition is not compatible with BizTalk Server 2004.
Note SQL Server and Analysis Server can be remote installations.
Install or update the following Windows components prior to installing BizTalk Server and all its components.
| Windows XP Windows Update |
Windows 2000 Server Windows Update |
Windows Server 2003 Windows Update |
|---|---|---|
| Windows XP Service Pack 1a | Windows 2000 Service Pack 4 | |
| Microsoft XML Core Services (MSXML) 4.0 with Service Pack 2 | Microsoft XML Core Services (MSXML) 4.0 with Service Pack 2 | Microsoft XML Core Services (MSXML) 4.0 with Service Pack 2 |
| Microsoft XML Core Services (MSXML)3.0 with Service Pack 4 | Microsoft XML Core Services (MSXML)3.0 with Service Pack 4 | Microsoft XML Core Services (MSXML)3.0 with Service Pack 4 |
| Microsoft .NET Framework 1.1 | Microsoft .NET Framework 1.1 | Microsoft .NET Framework 1.1 |
| Microsoft Data Access Components (MDAC) 2.8 | Microsoft Data Access Components (MDAC) 2.8 | |
| SQLXML 3.0 with Service Pack 2* | SQLXML 3.0 with Service Pack 2* | SQLXML 3.0 with Service Pack 2* |
| Microsoft Internet Explorer 6 Service Pack 1 | Microsoft Internet Explorer 6 Service Pack 1 | |
| Microsoft Office Web Controls 10 | Microsoft Office Web Controls 10 | Microsoft Office Web Controls 10 |
| Updates Q828758, Q329433, and Q831950** | Updates Q828748, Q329433, Q821887, and Q831950** | Update Q831950** |
Note * You must install Microsoft .NET Framework 1.1 before you install SQLXML 3.0. When installing SQLXML 3.0 you may be prompted to install SOAP Toolkit 2.0. The SOAP Toolkit is not required for BizTalk Server 2004. Installation of the SOAP Toolkit is optional.
Note ** Update Q831950 must be installed on the computer(s) where SQL Server 2000 is installed.
For more information about installing these components, go to the Microsoft Download Center at (http://go.microsoft.com/fwlink/?LinkId=16929), and search for the component by name.
For more information about known issues in BizTalk Server 2004, see Knowledge Base article 834624 located at http://go.microsoft.com/fwlink/?LinkId=22784.
If you are configuring Business Activity Services (BAS) the minimum software requirement for a client computer includes:
If you are using the Single Sign-On (SSO) client utility (ssoclient.exe), the minimum requirement for a client computer includes:
The SSO client package is available as a self-extracting file (SSOClientInstall.exe) installed with the SSO administration feature. The SSOClient.exe enables users to configure their client mappings in the credential database.
Note The managed interoperability component of the SSO client utility is installed only if Microsoft .NET Framework 1.1 is installed on the client computer.
The installation of the stand-alone SSO client (ssoclient.exe) and SSO administrative utilities (ssomanage.exe and ssoconfig.exe) does not create shortcuts on the Start menu to access the command line utilities. To run the SSO client or SSO administrative utilities after installation, you must open a command prompt and navigate to the SSO directory: \Program Files\Common Files\Enterprise Single Sign-On.
To install BizTalk Server 2004 by using the BizTalk Server 2004 Installation Wizard, you must log on as an administrator or as a user who is a member of the local administrators group. You must also have administrative privileges on the SQL Server that you will be using. When using Terminal Services to install BizTalk Server you must be a local administrator on the computer on which you are installing BizTalk Server.
If you plan to install BizTalk Server 2004 and SQL Server on two different computers, and you plan to use local user and group accounts, the exact same user account and the exact same group account names must be used on both the local and the remote computers. The default group names are:
Note This is the identity of the application pool that SharePoint runs under.
It is highly recommended that you install the SSO master secret server as a stand-alone server. Install the Enterprise Single Sign-On Runtime feature as part of a custom installation. For more information about custom installations, see Performing a Custom Installation.
Note The SSO Administrators groups gets created automatically on the SQL Server if local group accounts have been specified and the user running the Configuration Wizard has administrator privileges on the remote computer.
For more information about setting up the appropriate groups, see Establishing Secure Group Accounts in the BizTalk Server Documentation installed with BizTalk Server.
For information about configuring SSO in a cluster environment, see Best Practices for Clustering the Master Secret Server in the BizTalk Server Documentation.
This section includes information about installing prerequisite software prior to installing Microsoft BizTalk Server 2004.
Microsoft Windows 2000 Server with Service Pack 4 (SP4), Windows XP Professional with Service Pack 1, or Windows Server 2003 is required for all BizTalk Server 2004 installations. This installation guide includes information regarding the necessary configuration of Windows in combination with BizTalk Server.
Note You must install Windows Server 2003 on your computer in order to use Business Activity Services with Windows SharePoint Services. If you do not install these prerequisites, and you select a complete installation, you cannot configure Business Activity Services.
BizTalk Server 2004 development tools are based in Visual Studio .NET 2003. You must install Visual Studio .NET 2003 with C# on your computer prior to installing BizTalk Server 2004 development tools.
When the installation wizard completes, you will have the option of running the BizTalk Server Configuration Wizard. To complete the BizTalk Server configuration you must have SQL Server 2000 with Service Pack 3a installed on your computer or accessible remotely.
For more information, see Minimum Software Requirements.
This section contains:
These installation requirements include information regarding the necessary configuration of Windows in combination with SQL Server, Visual Studio .NET, Windows SharePoint Services, and BizTalk Server 2004.
Microsoft Windows Server 2003 is required for a complete installation of BizTalk Server 2004, which includes Business Activity Services. This setup also requires Windows SharePoint Services.
You can also use Microsoft Windows 2000 Server for a complete installation of BizTalk Server 2004, however during the installation process you will receive a message indicating that Business Activity Services will not be installed.
You can use Microsoft Windows XP Professional in development environments.
Additional Windows requirements include Internet Information Services (IIS) and ASP.NET.
After installing Windows you must be logged on as an administrator, or add a Windows user account to the Administrators group in order to install additional software.
This section contains:
If Windows 2000 Server, or Windows XP Professional is not installed on your computer, go to the Microsoft Windows Web site ( http://go.microsoft.com/fwlink/?LinkId=17552) for more information about purchasing and installing Windows.
If you have Windows 2000 Server or Windows XP Professional installed on your computer, ensure that you meet the requirements listed below.
Observe the following requirements:
For a complete installation of BizTalk Server 2004 on Windows 2000 or Windows XP, the following software must be installed.
Note Update Q831950 must be installed on the computer(s) where SQL Server 2000 is installed.
If Windows Server 2003 is not installed on your computer, go to the Microsoft Windows Web site (http://go.microsoft.com/fwlink/?LinkId=17552) for more information about purchasing and installing Windows Server 2003.
You must install Windows Server 2003 if you plan to include Business Activity Services with your installation of BizTalk Server. Business Activity Services is dependent on Windows SharePoint Services, which you can only install on Windows Server 2003. For information about installing and configuring Windows SharePoint Services, see SharePoint Services Prerequisites and Installation Requirements in the BizTalk Server Documentation.
Observe the following requirements for Windows Server 2003:
Important IIS is set to IIS 5.0 isolation mode, if you upgraded from Windows 2000 to Windows Server 2003. You must turn off IIS 5.0 isolation mode. To do this click Start, click Control Panel, double-click Administrative Tools and then double-click Internet Information Services (IIS) Manager. In the Internet Information Services (IIS) Manager dialog box, right-click Web Sites, and select Properties. On the Service tab, clear the Run WWW service in IIS 5.0 isolation mode check box.
International When using a German version of Windows Server 2003 Server you must enable network DTC access before installing the English version of BizTalk Server. To do this select Add/Remove Windows Components, select Application Server, and then select Enable network DTC access. You must enable Network Clients security settings if clients need to connect to the DTC that is running SQL. To do this, select Component Services, right-click My Computer, and then click Properties. In the My Computer Properties dialog box, on the MSDTC tab, click Security Configuration. In the Security Configuration dialog box, select Network Clients.
For a complete installation of BizTalk Server 2004 on Windows Server 2003, the following software must be installed.
Note Update Q831950 must be installed on the computer(s) where SQL Server 2000 is installed.
You must install and enable IIS and ASP.NET before you can publish BizTalk orchestrations and schemas as Web services.
If you did not select Internet Information Services (IIS) on the Windows XP Professional Components page during setup of Windows XP Professional, use the following procedures to install it.
Important The version of IIS included with Windows XP allows only a maximum of 10 simultaneous TCP connections. It is not as versatile or as powerful as the one shipped with Enterprise versions of Windows 2000 Server or Windows Server 2003.
Note Microsoft Windows 2000 Server installs IIS by default. Verify that IIS is enabled.
To install Internet Information Services (IIS)
Note In Windows Server 2003 select Application Server in the Components list, and then click Details.
Note There may be several other IIS components selected by default. These components are optional.
Warning By default IIS 6.0 configuration does not allow ISAPI extensions. You must explicitly configure this before using BizTalk Server HTTP receive handlers.
For more information about installing and enabling ASP.NET on Win2K, WinXP, and Win2K3, see: http://go.microsoft.com/fwlink/?LinkId=21100
BizTalk Server 2004 development tools are based in Visual Studio .NET 2003. Therefore, you must have Visual Studio .NET 2003 with C# installed on your computer prior to installing BizTalk Server 2004 development tools. For more information, see Minimum Software Requirements.
This section contains:
For installation instructions for Visual Studio .NET 2003, go to Visual Studio .NET Web site on MSDN http://go.microsoft.com/fwlink/?LinkId=17557.
Important You must start Microsoft Internet Information Services (IIS) before you install Visual Studio .NET.
Important You must select Visual C# as an option when you install Visual Studio .NET.
To install Visual Studio .NET
Important To work with the BizTalk Server 2004 development tools you must select Visual C# as one of the options.
Installing the full Visual Studio .NET suite will take several minutes.
Important You must also install the Visual Studio product documentation for BizTalk Server F1 Help to work in the Visual Studio environment. If you do not install the Visual Studio product documentation and you attempt to use F1 help for BizTalk Server you will receive an error message stating that help is not installed for Visual Studio.
When you configure BizTalk Server, the configuration process creates several BizTalk Server databases. Prior to configuring BizTalk Server 2004, you must install Microsoft SQL Server 2000 with Service Pack 3a (SP3a), or have remote access to an installation of SQL Server.
SQL Server 2000 Analysis Server is optional. It is required only if you want to use Health and Activity Tracking (HAT). If you install SQL Server 2000 Analysis Services, you must also install SP3a for Analysis Services.
This section contains:
During BizTalk Server configuration, BizTalk Server prompts you for the SQL Server computer and database information necessary to configure BizTalk Server databases. If you plan to install BizTalk Server 2004 and SQL Server on two different computers, and you plan to use local user and group accounts, you must use the same user account and the same group account names on both the local and the remote computers. For more information, see Minimum Security Requirements.
SQL Server Administrative privileges are required to run the Configuration Wizard and configure the necessary databases. If you plan to use a remote SQL Server, you must establish these privileges on the remote computer before you run the BizTalk Server 2004 Configuration Wizard.
For more information about configuring BizTalk Server using a remote SQL Server, see the Configuration information contained in the BizTalk Server Documentation. To use the documentation after you install BizTalk Server 2004, on the Start menu, point to Programs, point to BizTalk Server 2004, and then click BizTalk Server Documentation.
To install SQL Server, insert the Microsoft SQL Server compact disc into the CD-ROM drive and follow the on-screen instructions. The setup wizard walks you through the steps necessary to install SQL Server.
Observe the following requirements:
Microsoft BizTalk Server 2004 supports collations commonly associated with BizTalk Server 2004 language versions. BizTalk Server 2004 is available in English, French, German, Italian, Japanese, Korean, Simplified Chinese, Spanish and Traditional Chinese.
The exact list of supported collations is:
If SQL Server is installed on a computer with system locale corresponding to one of these languages the appropriate collation is set during the default installation of SQL Server. In all other instances, the collation must be set during a custom install of SQL Server to one of the collations listed above. Make sure that the collation selected is neither case sensitive nor binary. If the SQL Server has a binary or case sensitive collation, the BizTalk Service may fail to install.
Warning When using the SQL Server shared memory network library with BizTalk Server 2004 you might experience a degradation in performance under certain stress conditions, if clients are accessing SQL Server from the same box. To resolve the problem disable the use of the shared memory network library in the SQL Client Network Utility. To disable shared memory network library, open the SQL Server Client Network Utility and clear the Enable shared memory protocol check box.
After you install SQL Server, you must install SQL Server Service Pack 3a (SP3a). For more information about SP3a, go to http://go.microsoft.com/fwlink/?LinkId=17558/.
SQL Server 2000 Analysis Services is optional. It is required only if you want to use Health and Activity Tracking (HAT) or Business Activity Monitoring. If you install SQL Server 2000 Analysis Services, you must also install Analysis Services SP3a.
Before installing BizTalk Server 2004, verify that the SQL Server that will host the BizTalk Server databases is running. This is especially important if you plan to run the BizTalk Configuration immediately after you install BizTalk Server. The Configuration Wizard will create several BizTalk Server databases.
Important SQL Server Agent must also be running on each SQL Server that hosts a BizTalk MessageBox database.
To verify that SQL Server is running
The SQL Server Service Manager dialog box appears.
If it is not, click the drop-down arrow to view a list of available servers and scroll to locate your server.
The service is running if the Start button in the dialog box is unavailable. In addition, at the bottom of the dialog box is a message that states that the service is running.
Microsoft Windows SharePoint Services is required prerequisite software for a complete installation of BizTalk Server, which includes Business Activity Services. You can only install Windows SharePoint Services on Windows Server 2003. For more information, see Installing Microsoft Windows Server 2003. If you do not install Windows SharePoint Services, Business Activity Services will not be installed with BizTalk Server.
The section contains:
Microsoft Windows SharePoint Services is available for download at: http://go.microsoft.com/fwlink/?LinkId=18109.
Refer to the "Windows SharePoint Services Administrator's Guide" at http://go.microsoft.com/fwlink/?LinkId=18110 for further information about installing SharePoint Services. You should also review the readme file included in the download for details about known issues.
Important Windows Server 2003 must be running as a Web server running Internet Information Services 6 in IIS 6 worker process isolation mode, and you must enable ASP.NET on the server prior to installing SharePoint Services. For more information, see Installing Microsoft Windows Server 2003.
When installing Windows SharePoint Services, observe the following requirements:
When the SharePoint Services installation is complete, the SharePoint Central Administration page opens.
You can now configure an administration site and apply SharePoint Services to a virtual server using SharePoint Central Administration. For more information, see Configuring Windows SharePoint Services.
After you install Windows SharePoint Services, you must configure an administration site and must apply SharePoint Services to a virtual server. This is called extending. You must extend a virtual server with SharePoint Services before you can create a SharePoint Services Web site.
To configure Windows SharePoint Services, observe the following requirements:
Note You cannot configure SharePoint Services if FrontPage Server Extensions are running on the virtual server. For more information, see http://go.microsoft.com/fwlink/?LinkId=21690.
Important By default, Microsoft Windows SharePoint Services includes the root of the IIS default Web site as a managed path. To create a virtual directory on a SharePoint Services-extended virtual server for your own use, for example, for a BizTalk Server receive location or for a Web service application, you must exclude the URL for your virtual directory from the SharePoint Services managed paths. Alternatively, if you have not configured a top-level SharePoint Services site on the root of the IIS web site, you may remove the root as a managed path.
See the "Managing Paths" section in Microsoft Windows SharePoint Services Administrator's Guide at http://go.microsoft.com/fwlink/?LinkId=18110 for information about how to manage paths from the command line.
See the Microsoft SharePoint Products and Technologies v.2.0 Software Development Kit for more information about creating Web applications on a SharePoint Services-extended virtual server.
To verify that SharePoint is configured correctly
You should see your new Web site. This indicates that SharePoint is working correctly.
To delete this site, return to SharePoint Central Administration (to the home page) and select Delete Site Collection. Type the complete URL for the site to delete and then confirm the deletion.
Important If the SharePoint Configuration database, Content database, and BizTalk Server 2004 exist on different computers, and if you use Windows authentication to access those databases, then you must have db_owner permissions on these databases when running BizTalk Server 2004 configuration. After BizTalk Server configuration is complete, these permissions should be removed from the SharePoint Configuration and Content databases.
Important Before installing BizTalk Server 2004 you must comply with the minimum hardware and software requirements. To ensure that you have implemented the prerequisites, review the Hardware, Software, and Security Requirements.
Important Do not install BizTalk Server 2004 on a computer that already has BizTalk Server 2000 or BizTalk Server 2002 installed.
International Installing BizTalk Server 2004 on computers whose names contain letters outside of the following set should not be used: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only computer names that contain the letters in this set are supported.
This section contains:
A complete installation of BizTalk Server requires Windows in combination with SQL Server, Visual Studio .NET, Windows SharePoint Services, and various Windows Components. To perform a complete installation, ensure that the minimum hardware software and security requirements have been met. For more information, see Hardware, Software, and Security Requirements.
Warning Close all other programs before installing BizTalk Server 2004.
Warning During the installation process IISAdmin (along with its dependent services), will be stopped and restarted.
To perform a complete installation of BizTalk Server
If the BizTalk Server 2004 setup page does not appear, double-click setup.exe located in the root of the installation CD.
Important During the installation process the Windows Management service is stopped and restarted.
International The installation path must not contain letters outside of the following set: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only installation paths that contain the letters in this set are supported.
Note If you do not install all the prerequisite software, some components will not be installed. For more information, see Installing Prerequisite Software.
The Configuration Wizard appears.
Important It is recommended that you review the configuration documentation before you configure BizTalk Server. Do not select the Start Configuration Wizard check box, if you intend to review the documentation first. On the Start menu, point to Programs, point to BizTalk Server 2004, and click BizTalk Server Documentation and review the documentation. For information about configuring BizTalk Server 2004, see "BizTalk Server 2004 Configuration" in the Deployment section of the BizTalk Server Documentation.
The following table indicates which dependencies must be installed or updated before installation based on the features you select.
Warning During the installation process IISAdmin (along with its dependent services), will be stopped and restarted. ENTSSO, RuleEngineUpdateService, and EDI Subsystem NT services will also be stopped and re-started if SSO, Rules Engine and EDI are installed.
| Feature | WSS | MDAC 2.8 | .NET Framework 1.1 | VS .NET 2003 | MSXML 4.0 SP2 | IE6 SP1 | SQL Client Tools | SQLXML 3 SP2 | OWC10 |
|---|---|---|---|---|---|---|---|---|---|
| Documents | |||||||||
| Development | X | X | X | X | |||||
SDK |
X | X | X | X | |||||
| Runtime Components | |||||||||
Engine |
X | X | X | X | X* | X | |||
| HWS Runtime Components |
X | X | X | X | |||||
| Base EDI Adapter |
X | X | X | X | |||||
Rules Engine |
X | X | X | X | |||||
Enterprise Single Sign-On |
X | X | |||||||
| Admin and Monitoring | |||||||||
Admin Tools |
X | X | X | X | X* | X | |||
| HWS Admin |
X | X | X | X | |||||
Enterprise Single Sign-On Admin |
X | X | |||||||
| Information Worker Application/Portal | |||||||||
BAS |
X | X | X | X | X | ||||
Human Workflow Web Services |
X | X | X | X |
Note *If you will be using Business Activity Monitoring, ensure that SQL Client Tools are installed.
For more information about installing these components manually, go to the Microsoft Download Center at (http://go.microsoft.com/fwlink/?LinkId=16929), and search for the component by name.
In the custom installation screen, you have the option of selecting either Enterprise Single Sign-On Services (SSO), or the Engine, or both from the Runtime components.
In the custom installation screen, you have the option of selecting the SSO Administration feature.
Note If you have BizTalk Server 2004 Runtime, Development, or Administration features installed, you will not be able to uninstall the SSO Runtime or Administration components until those features are removed.
Important When performing a custom installation that only includes the Development option, two computers are required. You must perform a complete installation and configuration on the first computer, create a new BizTalk Group, and then on a separate computer perform a custom installation for Development only. During the Development-only installation, join the existing BizTalk group and specify the SQL Server where your group was created.
There are four Human Workflow Service (HWS) Components
To install HWS using multi-computer systems, the Runtime components, Administration Tools and Web Service component of HWS can be installed on separate stand-alone computers. The Development\SDK is not required.
To configure HWS using multi-computer systems you must configure the HWS Runtime components first.
Important You must install HWS Runtime components on a computer running Internet Information Services (IIS). Without IIS installed, HWS can only run HWS actions and cannot act as an HTTP receive location.
To install BAS without Active Directory or with BAS MSMQ signing turned off, the DisableBasMsmqSigning switch under the HKLM\Software\Microsoft\BizTalk Server\3.0\TPM registry path must have a value of 1. This switch should be set after installing BizTalk but before running the Configuration Wizard.
If you have already installed BizTalk Server and need to disable BAS MSMQ signing, complete the following steps.
To disable BAS MSMQ Signing
If you have already installed BizTalk Server with BAS MSMQ disabled and need to enable BAS MSMQ signing, complete the following steps.
To enable BAS MSMQ Signing
To perform a custom installation of BizTalk Server 2004
If the BizTalk Server 2004 setup page does not appear, double-click setup.exe located in the root of the installation CD.
International The installation path must not contain letters outside of the following set: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only installation paths that contain the letters in this set are supported.
The Configuration Wizard appears.
Important It is recommended that you review the configuration documentation before you configure BizTalk Server. Do not select the Start Configuration Wizard check box, if you intend to review the documentation first. On the Start menu, point to Programs, point to BizTalk Server 2004, and click BizTalk Server Documentation and review the documentation. For information about configuring BizTalk Server 2004, see "BizTalk Server 2004 Configuration" in the Deployment section of the BizTalk Server Documentation.
A silent installation is ideal for test scenarios or as part of a large-scale enterprise deployment. BizTalk Server 2004 provides command line parameters that can be used with setup.exe to perform a silent installation.
Configuring your BizTalk Server installation in silent mode can be done in conjunction with setup.exe or as a separate procedure, only after using the Installation and Configuration Wizards to complete an initial installation and configuration. The initial configuration will produce an XML file that is required for a silent configuration.
For more information about running the BizTalk Server 2004 Configuration Wizard in silent mode see, Silent Configuration in the BizTalk Server Documentation. To use the documentation after you install BizTalk Server 2004, on the Start menu, point to Programs, point to BizTalk Server 2004, and then click BizTalk Server Documentation.
This section contains:
There are two different modes of silent install. Both have their own required parameters and are mutually exclusive:
Note The following procedure will not configure BizTalk Server. For more information about running the BizTalk Server 2004 Configuration Wizard in silent mode see, Silent Configuration in the BizTalk Server Documentation. To use the documentation after you install BizTalk Server 2004, on the Start menu, point to Programs, point to BizTalk Server 2004, and then click BizTalk Server Documentation.
To perform a complete silent installation of BizTalk Server 2004
Setup.exe /addlocal all /INSTALLDIR “c:\Program Files\Microsoft BizTalk Server 2004” /l “c:\temp\BTSsetup.log” /InstallPlatform /AutologonPassword <password>
The following command line options must be used in conjunction with setup.exe:
Enterprise Single Sign-On (SSO) server and administration features are required. If you do not use /InstallPlatform to install Enterprise Single Sign-On server and administration features, you must run the SSO.msi before you run setup.exe. The SSO server is required for certain BizTalk Server features, including the Runtime Engine. For the silent installation scenario, you must install the SSO.msi beforehand using setup.exe.
The following parameters are optional:
International The installation path must not contain letters outside of the following set: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores ( _ ). Only installation paths that contain the letters in this set are supported.
Note In order to display additional options for command line installation, type setup.exe /? at the command prompt.
Note There should be no line break in the actual command line syntax.
Note Windows Installer command line options are not case sensitive.
Note For more information about the Windows Installer command line options, see Windows Help.
To perform a custom installation of BizTalk Server from the command line, use setup.exe along with the configuration snapshot (XML file) that is generated during the initial configuration.
Important These command line parameters will not work unless you have already installed and configured BizTalk Server and saved the configuration XML file.
Note The following procedure will not configure BizTalk Server. For more information about running the BizTalk Server 2004 Configuration Wizard in silent mode see, Silent Configuration in the BizTalk Server Documentation. To use the documentation after you install BizTalk Server 2004, on the Start menu, point to Programs, point to BizTalk Server 2004, and then click BizTalk Server Documentation.
To perform a custom silent installation of BizTalk Server 2004
Setup.exe /s “c:\Config.xml” /INSTALLDIR “c:\Program Files\Microsoft BizTalk Server 2004” /l “c:\temp\BTSsetup.log” /InstallPlatform /AutologonPassword <password>
The following command line parameters are used in step 6:
Note In order to display additional options for command line installation, type setup.exe /? at the command prompt.
Note There should be no line break in the actual command line syntax.
Note Windows Installer command line options are not case-sensitive.
Note For more information about the Windows Installer command line options, see Windows Help.
For more information about configuring BizTalk Server in silent mode, see Silent Configuration in the BizTalk Server Documentation. To use the documentation after you install BizTalk Server 2004, on the Start menu, point to Programs, point to BizTalk Server 2004, and then click BizTalk Server Documentation.
When you install BizTalk Server 2004, some files are added to or changed in folders other than the typical installation folders.
Warning If you uninstall BizTalk Server 2004, many of these files are not removed from your system automatically; you must remove them manually.
Upon installing BizTalk Server 2004, the following executable files in the System folder (system32) are installed, or updated to the latest version:
Use the Microsoft Windows Add/Remove Programs utility to remove Microsoft BizTalk Server 2004.
Observe the following:
To remove BizTalk Server 2004
Note Uninstalling BizTalk Server 2004 does not uninstall Enterprise Single Sign-On Services (SSO), you must manually uninstall it using Add/Remove Programs. You cannot uninstall SSO if you have a dependent BizTalk Server 2004 feature installed on the same computer.
To remove Enterprise Single Sign-On Services
Note If you have BizTalk Server 2004 Runtime, Development, or Administration features installed, you will not be able to uninstall the SSO Runtime or Administration components until all dependencies are removed.
This section includes an explanation of the log files and common error messages.
All dynamic information used by setup (upgrade information, error logs, etc.) will be located in the %Temp% directory. By default, the name of the file is Setup(mmddyy hhmm).log.
When setup is complete, the final screen gives you an opportunity to view the setup log and perform registration.
Problem: If Visual Studio .NET is open during installation, you might receive errors that will prevent a successful installation.
Resolution: Before you install BizTalk Server 2004, close Visual Studio .NET.
Problem: After installing BizTalk Server 2004 using Remote Desktop Terminal Services, various DLL files may fail to load properly.
Resolution: After installing and configuring BizTalk Server, log out of the terminal session and log back in before you attempt any other operations. This allows the updated %PATH% environment variable to be recognized by the remote session.
Problem: Health and Activity Tracking fails with the following error if Microsoft Office Web Controls 10 is not properly installed.
ActiveView.ColumnAxis is not null or not an object
Resolution: Type the following line at the command prompt:
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\Web Components\10\OWC10.DLL
Problem: When installing BizTalk Server 2004 you may encounter the following error:
Error 1303: The Installer has insufficient privileges to access this directory <BizTalk Install directory>\httpreceive. The installation cannot continue. Log on as administrator or contact your system administrator
Resolution:
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 1999-2004 Microsoft Corporation. All rights reserved.
Microsoft, Windows, BizTalk, SharePoint, Visual C#, Visual Studio, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.